Merged
Conversation
added 2 commits
April 23, 2026 20:48
The 7.0.26 package is already taken on npm, so this release-only lane moves the metadata to the next publishable patch and records the already-merged branch-start and PR-only finish fixes now shipping from main. Constraint: The shipped package payload had to stay aligned with already-merged mainline behavior\nRejected: Retry publishing 7.0.26 | npm rejects already-published versions\nConfidence: high\nScope-risk: narrow\nReversibility: clean\nDirective: Keep future publish-only bumps coupled to README release notes in the same change\nTested: node --test test/metadata.test.js; node --check bin/multiagent-safety.js; npm pack --dry-run; openspec validate agent-codex-release-guardex-7-0-27-2026-04-23 --type change --strict; openspec validate --specs; git diff --check\nNot-tested: Live npm publish and GitHub release creation before merge
The release change should carry its own PR reference so the follow-up handoff does not have to reconstruct which merge delivered the 7.0.27 metadata bump. Constraint: The release lane already had a live PR, so the evidence update had to land before merge\nRejected: Leave the PR URL only in chat output | cleanup bookkeeping drifts too easily\nConfidence: high\nScope-risk: narrow\nReversibility: clean\nDirective: Record the PR URL in the release change before merge whenever the cleanup section tracks it\nTested: git diff --check\nNot-tested: Post-merge cleanup fields that require final merged state
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Verification